The second group of date settings is used to specify which nodes DynRisk should interpret as “dates”. A DynRisk model typically contains nodes representing many different things, such as cost, time, decisions etc. In most cases DynRisk does not need to know what kind of node it is dealing with in order to compute its values. However, if a node is a “date” node, it is convenient to let DynRisk convert these values into a date format. To accomplish this, DynRisk needs a rule for how to distinguish date nodes from other nodes. You can choose between four different types of criterions:
• Kind is equal to…
• Name begins with…
• Code begins with…
• Unit begins with…
To select one of these, you click the “radio” button to the left of the criterion you want to apply.
If you select “Kind is equal to…”, you must choose a particular “kind” using the popup menu to the right. All nodes whose “kind” property is equal to the chosen one, will then be interpreted as a “date” node.
If you select “Name begins with…”, you must enter a name prefix into the field to the right. All nodes whose “name” property begins with this prefix, will then be interpreted as a “date” node.
If you select “Code begins with…”, you must enter a code prefix into the field to the right. All nodes whose “code” property begins with this prefix, will then be interpreted as a “date” node.
If you select “Unit begins with…”, you must enter a unit prefix into the field to the right. All nodes whose “unit” property begins with this prefix, will then be interpreted as a “date” node.
